Default Web Interface
The Controller's internal web interface is a very powerful diagnostic and management tool. You can view a Controller's web interface from within Designer or, for remote access, browse to the index page at http://xxx.xxx.xxx.xxx/default/index.lsp, where xxx.xxx.xxx.xxx is the IP address of the Controller.
Some pages may not always be visible if they aren't relevant to the current project file (or if there isn't a project loaded) e.g. IO Modules.
Use the navigation buttons across the top to select these pages:
Home
The home page provides general information about the status of the Controller: Serial number, type, IP address, loaded project details and memory usage. The bootloader Bootstrap loader; a small software program, stored in internal flash memory, that is responsible for loading the firmware or operating system. and firmware The embedded operating system, stored in internal flash memory or on the memory card. versions and MAC address are also given for reference.
The current uptime of the controller and last Boot Reason are shown to aid troubleshooting.
NOTE: The reset reason is not available on LPC X Rev2 or VLC
From here, it is also possible to download the project file that is currently running on the controller.
For the LPC X, VLC and VLC+ particular attention should be paid to the temperature readings; insufficient ventilation may cause the ambient temperature to rise and thus system & CPU temperatures to reach excessive levels, degrading performance.
Project Status
The status page provides feedback on the current state of playback:
Timelines
All timelines are listed with their current state and running time:
| --- | Inactive, the timeline has not run since the last reset |
| Running | The timeline is running and contributing to the output (items "on stage") |
| Running (Inactive) | The timeline is running in the background and not contributing to the output, generally because it has been overridden |
| Halted | The timeline is halted and contributing to the output |
| Halted (Inactive) | The timeline is halted in the background and not contributing to the output |
| Holding at End | The timeline is holding at end and contributing to the output |
| Holding at End (Inactive) | The timeline is holding at end in the background and not contributing to the output |
| Released | Inactive, the timeline has run but has been explicitly released |
In systems with more than one Controller it is important to understand that this timeline status is only pertinent to the Controller being accessed. For example, the accessed Controller may report that a timeline is Running (Inactive) because its fixtures are not contributing to the output while another Controller may well be Running (Active) because its fixtures are contributing to the output. In such systems the complete status can only be determined by interrogating all Controllers.
Scenes
All Scenes are listed with their current state:
| Started | The Scene is being played back on at least one fixture |
| Started (inactive) | The Scene has been started, but is not affecting the output, generally because it has been overridden |
| Released | The Scene is not being output |
In systems with more than one Controller it is important to understand that this scene status is only pertinent to the Controller being accessed. For example, the accessed Controller may report that a scene is Started (Inactive) because its fixtures are not contributing to the output while another Controller may well be Started because its fixtures are contributing to the output. In such systems the complete status can only be determined by interrogating all Controllers.
Groups
All groups are listed with their current intensity level.
Content Targets
On a VLC
Use this page in conjunction with the Control and Log pages to interrogate and debug an installation.
Log
The log can be cleared and saved to file using the Clear and Save buttons. Two types of log are provided:
General log
A blow-by-blow account of all activity including input/output,RS232 serial strings for example, and trigger matching. Extremely useful in helping debug complex interfacing and triggering arrangements. Alternatively, the log can be viewed directly from within Designer over an Ethernet or USB connection using View > Controller Log.
System log
A less verbose log of the Controller's system activity, useful for examining the boot-up sequence to help debug problems.
Log Filtering
Filter down the log to messages about specific topics using the filter buttons across the top of the log view.
You can also filter the log by text using the Text Filter box on the right hand side.
Show Lines
The Show Lines control allows you to specify how many lines of the log to display. The default is the last 50 lines.
Output
View output
Select the Protocol/DMX Port to examine a numerical snapshot of the control data being output, refreshed every 5 seconds. Select DVI to examine a graphical snapshot of the pixel matrix output.
The channel blocks will change colour depending on how the channel is being controlled:
| White | Playback |
| Grey | Unpatched |
| Blue Border | Output Live |
| Red border | Parked |
Use in conjunction with Control and Status pages to debug an installation.
A message will also be displayed if the selected output has been disabled by a Disable Output Action.
Park and Unpark
If authentication is active on a controller enter the username and password for an account with Control and/or Admin.
Park allows you to lock the value of a particular channel without actually altering your programming. This can be useful to turn off a fixture that is misbehaving temporarily or to make sure a working light stays on while you are programming.
Park can be accessed from the output view of the web interface, simply enter the channel or range of channels and the value at which to park. Parked channels are shown in red within the output view. There is the option to Unpark from the same view.
Parked channels will remain parked when you upload shows or output live. However all parked channels will be cleared if the Controller is reset or the power is cycled.
Input
Inputs
Use to examine the status of the Controller's inputs.
NOTE: Contact closure return High when the input is open and Low when the input is closed.
DMX
Select the DMX input to examine a snapshot of the DMX values being input, useful for debugging DMX triggering and control.
DVI
On LPC X or VLC
DALI
CSV Export
This information can be viewed in a comma separated values file by clicking the Save button. Copy, paste and save the information you require in a separate document.
Emergency Test Schedule
Only populated if the current interface has emergency ballasts present. View information about when Emergency Ballast tests are due to take place as well as the time and date of previous tests. Also view the uptime of the DALI bus.
Emergency Ballast Errors
Lists all reported errors reported by emergency fixtures on the current DALI interface. Errors will show ballast address, tests failed and reported errors.
Once a ballast has been repaired it can be marked as fixed here or by using triggers. Once a ballast has been marked as fixed it will remain in the Ballast Errors section until a subsequent test has confirmed that the fixture is indeed operational again.
Ballast Status
Lists all ballasts and reported status on the current interface. Standard ballasts show the ballast Address, Name, Status and Level; emergency ballasts also show Battery Charge, Emergency Lamp Hours and Total Lamp Hours.
Refresh Ballast Status
Sends the DALI commands to refresh the status of all ballasts on the interface, and updates the table.
Last Status Check
The date and time when a ballast’s status was last updated.
Refresh Status
Sends the DALI commands to refresh the status of a specific ballast on the interface.
Recent Power Failures
Lists any reports of bus power failures for the current interface.
Network
The Network Page allows access to all the devices in the project.
IO Modules
The IO Modules Page will list all the IO Module instances in use that are able to provide feedback of data or settings.
Control
A Controller can be controlled remotely in two ways:
Command line
An advanced feature that allows direct control of a specific Controller's fixtures, timelines and even DMX channels via the script engine, see command line reference.
Alternatively the command line can be customised to run as a Lua Trigger script, see web interface settings for details.
Triggers
Triggers in the project, together with user annotation, are listed here and can be fired by clicking on them. Since a network of multiple Controllers share triggers, firing triggers from one Controller's web interface will trigger all the Controllers in the project.
NOTE: Triggers set to Hidden in the project will not be displayed
Triggers on the default Control web page will not test conditions by default, check the Test Conditions box to text conditions before firing the trigger.
Dynamic text slots
All the Dynamic text slots are listed with their current value. You can edit any text slot and changes will take effect according to the preset settings on the timeline (immediately, next cycle, on timeline restart).
File Manager
Optionally, files can be uploaded to the controller's SD Card using the File Manager tab within the web interface.
Configuration
Allows you to change any of the controller configuration options as described in Controller configuration.
All the Controller's configuration settings are displayed and can be changed here, see configuration for details.
Remote upload
In addition, at the bottom of the page, is the means to upload a project file remotely via the web interface as an alternative to uploading directly from Designer. See the network section to learn how to generate a file for remote uploading.
IMPORTANT: Controllers must be running the same version of firmware The embedded operating system, stored in internal flash memory or on the memory card. as the Designer software. Uploading a project file to a Controller running different firmware may result in the project failing to load and run. Check the Controller's home page to determine compatibility before attempting a remote upload.
Custom Page
If a Custom Web Interface has been added, this can be accessed from the dropdown in the top right hand corner.
Log In
If the project has been configured with any user access accounts, then to access the web interface, users must use the Log In option in the top right.
This login uses the user names and passwords specified in the Project > Web Interface tab.
If authentication is active on a controller enter the username and password for a user account.
NOTE: The web interface uses Web Socket connections (RFC 6455), and some managed networks and proxy servers block these connections. If you don't see the web interface populating with data, please check whether your network is blocking web sockets
NOTE: Sometimes Ad-blockers can affect access to controllers with passwords set. If issues are seen, the controller's IP Address should be Whitelisted.
Related Topics